Most objects on a CygNet Studio screen are used to show point information, such as a point’s value, timestamp, description, etc. Many of the standard tool objects, such as Text Tool objects, show information from specific point. This point is referred to as the object’s primary point. Other objects, such as a Group Grid Tool object, show information from multiple points. Tools that can be configured with a primary point are identified in the icon by a small red "C," such as the Text Tool
.
To show point information, an object must identify the point using a fully qualified CygNet tag string. The valid tag string formats are listed in the table below.
|
Format |
Components |
|---|---|
|
Tag String |
SITE.SERVICE.POINTID |
|
Long Tag String |
SITE.SERVICE:LONGID |
|
Facility Tag String |
SITE.SERVICE::FACILITY.UDC |
Primary point objects include the properties [1:SiteService], [2:Point ID], [3:Long Point ID], [4:Facility ID], and [5:UDC] for identifying the point. Only the minimum number of components required to build the tag string have to be used. For example, to associate an object with a point using its Point ID, the "Tag String" format would be used. This format requires use of the [1:SiteService] and [2:Point ID] properties.
The recommended CygNet tag string format is the Facility Tag String. This format is recommended because both the Site.Service and Facility components can be defaulted using TheView’s [SiteService] and [Facility] properties, requiring the object to identify only its UDC(s). For primary point objects this is done using the [5:UDC] property. For objects that show information for multiple points, there is a UDC selector.
For template screens, the Facility Tag String format is required with the [SiteService] and [Facility] properties specified for TheView.